Methods for dynamic router configuration in a mesh network

ABSTRACT

A method for router configuration includes: at a router, collecting DHCP server presence data of a local area network; at the router, collecting NAT server presence data of the local area network; generating a network configuration status based upon the DHCP server presence data and the NAT server presence data; and configuring DHCP server and NAT server settings of the router based on the network configuration status.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/641,537, filed 5 Jul. 2017, which is a division of U.S. applicationSer. No. 15/131,472, dated 18 Apr. 2016, which claims the benefit ofU.S. Provisional Application Ser. No. 62/161,652, filed on 14 May 2015,all of which are incorporated in their entirety by this reference.

TECHNICAL FIELD

This invention relates generally to the computer networking field, andmore specifically to new and useful methods for dynamic routerconfiguration in a mesh network.

BACKGROUND

The modern internet has revolutionized communications by enablingcomputing devices to transmit large amounts of data quickly overincredibly vast differences. The rate of innovation set by applicationand web developers is breathtakingly fast, but unfortunately, not allaspects of the internet experience have kept pace. In particular, evenas people rely more and more heavily on home networking solutions toenable internet connectivity for a rapidly increasing collection ofelectronic devices, the technology underpinning those solutions oftenprovides a woefully inadequate user experience. In particular, it isoften difficult for users to configure home networking solutionscorrectly in scenarios involving more than one networking device (e.g.,routers, switches, gateways, etc.); for example, wireless mesh networks.Thus, there is a need in the computer networking field to create new anduseful methods for dynamic router configuration in a mesh network.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a chart representation of a method of a preferred embodiment;

FIG. 2 is a diagram representation of a mesh network using smartrouters;

FIG. 3 is a diagram representation of a smart router;

FIG. 4 is a chart representation of a network configuration detectionstep of a method of a preferred embodiment; and

FIGS. 5A and 5B are signal flow representations of configuration datareceipt techniques of a method of a preferred embodiment;

FIGS. 6A and 6B are signal flow representations of signal responsedelays without and with NAT delays respectively,

FIGS. 7A and 7B are example representations of NAT detection of a methodof a preferred embodiment;

FIG. 8 is a schematic representation of physical LANs linked via VPNtunnel;

FIG. 9 is a chart representation of NAT/DHCP server configuration stepof a method of a preferred embodiment; and

FIGS. 10A and 10B are example representations of user intervention of amethod of a preferred embodiment.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description of the preferred embodiments of the inventionis not intended to limit the invention to these preferred embodiments,but rather to enable any person skilled in the art to make and use thisinvention.

A method 100 for dynamic router configuration in a mesh network includesdetecting a network configuration S110 and configuring router DHCP andNAT settings S130 based on the network configuration, as shown inFIG. 1. The method 100 may additionally include communicating networkstatus with a remote management platform S120, configuring routerfirewall settings S140, and/or prompting user intervention S150.

The method 100 functions to enable smart routers to configure themselvesto best suit a user's particular home network configuration. Inparticular, the method 100 preferably enables multiple smart routers towork together to create a wireless mesh network, blanketing a space inwireless network coverage, as shown in FIG. 2.

Typically, to configure an internet-connected wireless mesh network, auser must configure a first router to serve as a gateway to the internet(e.g., by connecting the router to a cable modem). Further, somenetworking device (generally the aforementioned first router) must alsobe configured to serve as a network address translation (NAT) server, adynamic host configuration protocol (DHCP) server, and a wireless accesspoint. Then, to extend wireless coverage as shown in FIG. 2, additionaldevices (e.g., wireless routers, access points, repeaters) must beadded. Even in the simple case of two or three wireless access points,the configuration options are virtually endless. For example, the accesspoints could exist on a single bridged network, or could be separatedinto different networks (e.g., could be assigned to different VLANs).The access points could be connected to each other by Ethernet cables,or simply serve as wireless repeaters. The access points could shareavailable Wi-Fi channel space in any number of ways.

Even for experienced users, the array of network configurationsavailable can be extremely overwhelming. The method 100 functions toperform much of this configuration both automatically anddynamically—optimizing the network for a user's needs without requiringextensive computer networking knowledge or hassle.

The method 100 may additionally be used to configure smart routers toaddress issues other than those posed by wireless mesh networking; forexample, the method 100 may enable a home network to make efficient useof multiple wide area network (WAN) gateways (e.g., splitting trafficacross them, using one WAN access point as backup for another, etc.).

The smart routers described herein are preferably substantially similarto those described in U.S. patent application Ser. No. 15/008,251, theentirety of which is incorporated by this reference. Additionally oralternatively, the smart routers may be any suitable networking devices.

Smart routers implementing the method 100 preferably include a Wi-Firadio, a Bluetooth radio, an Ethernet interface, and a processor. Therouter may additionally or alternatively include any other hardware orsoftware. In one example implementation, as shown in FIG. 3, a smartrouter includes two Wi-Fi radios: one 5 GHz radio, and one switchableradio (that may operate at either 5 or 2.4 GHz), a personal area network(PAN) such as Bluetooth radio capable of both Bluetooth 4.0 and BTLEcommunication, an auto-sensing gigabit Ethernet interface, an ARMprocessor, DDR RAM, EMMC storage (for router firmware), and a USBinterface (e.g., for adding network-accessible storage).

Smart routers operating the method 100 are preferably configured and/ormanaged by a remote management platform. In one example, smart routersmay be configured by altering stored configuration profiles in a remoteserver (part of the remote management platform), after which the storedconfiguration profiles are pushed to the smart routers. This techniqueis particularly useful in mesh networking applications; if the remotemanagement platform is aware that three smart routers are intended foruse in a single network, the remote management platform can attempt tobridge the networks of the three routers regardless of physical locationor existing network topology.

The method 100 is preferably performed by smart routers (eitherindependently or cooperatively), but may additionally or alternativelybe performed by any other suitable computing device. For example, asdescribed in later sections, some steps of the method 100 may beperformed by a remote management platform.

While the method 100 is described throughout this application as beingapplicable to home networks, a person skilled in the art will recognizethat such a system can be applied to any suitable network (such as onein a small business). The method 100 is preferably intended for use inscenarios where enterprise networking solutions (and the support staffto maintain them) are not feasible; additionally or alternatively, themethod 100 may be used in any suitable scenario (e.g., in typicalenterprise networking scenarios).

Step S110 includes detecting a network configuration. Step S110functions to provide a router with information about the network towhich the router is connected. In particular, Step S110 preferablyfunctions to provide the router with information about other routers onthe network (useful for mesh networking) and/or information aboutpotential gateways to the internet (useful for the router to provideconnectivity to the internet).

Step S110 preferably includes detecting the path between the router andone or more internet gateways, but may additionally or alternativelyinclude detecting any other relevant network configuration information(e.g., identity of devices on the network, presence and configuration ofDHCP, NAT, and/or DNS servers, presence and configuration of firewalls,available LAN/WAN bandwidth, etc.).

Step S110 is preferably performed upon initial configuration of arouter, but may additionally or alternatively be performed at anysuitable time; for example, upon detection of network changes (e.g.,detection of an additional router, detection of router configurationchanges, detection of changes to internet connectivity, detection ofdecreased quality of service, detection of high latency, detection ofpacket loss), at the request of a network administrator or the remotemanagement platform, or upon expiration of some time threshold (e.g.,every five days). Step S110 can be performed automatically (e.g.,conditioned on a particular feature or changes to a particular featureof the network), manually (e.g., when prompted by a user), or in anyother suitable manner. If Step S110 is initiated manually, the userpreferably has the option of doing so via any means; e.g., physically(e.g., by pushing buttons located physically at the router), remotely(e.g., by requesting it via a remote management platform, by means of anapplication installed on an external electronic device, etc.), etc.Performing Step S110 may also include detecting network configurationdata using both automatic and manual aspects; for example, Step S110 canbe initiated automatically and automatically detect network featureswhile also (either simultaneously or sequentially) soliciting input fromthe user to aid in gathering network configuration data.

Step S110 preferably includes attempting to establish an internetconnection S111 and analyzing internet connection paths S112, as shownin FIG. 4.

Step S111, attempting to establish an internet connection, functions toenable a router to determine information about a network's internetconnectivity (or lack thereof). Step S111 may also function to allow arouter to connect to a remote management platform to downloadconfiguration data, or to perform network analysis (e.g., as describedin Step S112).

Step S111 preferably includes requesting a DHCP-assigned IP address. Ifa DHCP-assigned IP address is received, the IP address can be used toperform some analysis of the network path. In particular, receiving aDHCP-assigned IP address can be an indication that a DHCP server (or,possibly, multiple DHCP servers) already exists on the local areanetwork; alternatively or additionally, receiving a DHCP-assigned IPaddress can indicate the presence of a pre-existing internet connection(or, possibly, multiple pre-existing internet connections), can be usedto analyze the network topology between various DHCP servers and othernetwork entities (e.g., other routers, switches, external servers, etc.)on the local area network, or can be used for any other suitablepurpose. In addition to receiving a DHCP-assigned IP address, requestinga DHCP-assigned IP address may include receiving additional informationthat may be used to perform network path analysis; for example, therouter address, DNS addresses, DHCP lease time, and/or a subnet maskassociated with a DHCP lease may be received along with theDHCP-assigned IP address and may be used to perform networkconfiguration analysis. If a DHCP-assigned IP address is not received,this may be an indication that the router is not connected to a LAN orWAN (or that a DHCP server is not running on a connected LAN).

Step S111 preferably includes attempting to establish an internetconnection via an Ethernet port of the router or through an openwireless network, but may additionally or alternatively includeattempting to establish an internet connection in any suitable manner.

In one embodiment, other configured routers broadcast a restricted opennetwork. The restricted open network is preferably hidden (i.e., it doesnot broadcast its SSID). Alternatively, the restricted open network maynot be hidden. In this embodiment, routers attempting to connect to theinternet during configuration may connect to any nearby router'srestricted open network. The restricted open network preferably onlyallows access to cloud servers used for routerconfiguration/registration; additionally or alternatively, therestricted open network may allow any suitable access. For example, therestricted open network may allow communication with Windows updateservers as well. The restricted open network preferably allowsconnections with any device requesting to join; additionally oralternatively, the restricted open network may only allow devices withcertain credentials or characteristics to connect. As a first example,the restricted open network may only allow devices with a particular MACaddress prefix (e.g., the prefix corresponding to the routermanufacturer) to connect. As a second example, the restricted opennetwork may require an access code or cryptographic key, certificate,etc. for a device to connect to the network. As a third example, therestricted open network may only be joined after initiation ofout-of-band communication (e.g., the router attempting to join a secondrouter's restricted open network must establish communication with thesecond router over Bluetooth or another non-WiFi protocol, for example,over a PAN connection). Devices connecting to the restricted opennetwork are preferably isolated from other devices (e.g., on the mainnetwork associated with the router broadcasting the restricted opennetwork) using a virtual LAN. Alternatively, devices joining therestricted open network may have any level of access to devices on theprimary network or on other virtual networks (e.g., no access, limitedaccess, full access). In this example, the virtual LAN can enable therouters and servers on the restricted open network to register with aremote management platform, retrieve router configuration updates,and/or download server updates (among other functions) while stillenabling network security by barring unwanted connections and traffic onthe local area network. In some realizations, the virtual LAN on therestricted open network can also prevent abuse of the restricted opennetwork by restricting bandwidth, limiting the accessible sites thatdevices on the restricted open network can access, hiding other devicesalready connected, and/or any other suitable means.

If Step S111 is not successful in establishing an internet connection(or for any other reason), Step S111 may include attempting to connectto another device in order to secure an alternative internet connection.In one example, the device can be a smartphone, and Step S111 mayinclude attempting to connect to the internet via the cellular internetconnection of the smartphone, as shown in FIG. 5A.

Alternatively, Step S111 may include attempting to connect to aconfiguration application on another device (e.g., a smartphone) via aPAN such as Bluetooth (e.g., capable of at least Bluetooth 4.0 and BTLEcommunication), Zigbee, etc., or Wi-Fi to receive configuration datalocally from the device (e.g., the smartphone may download configurationdata from the router management platform to the configuration app, andthen the router may in turn receive that configuration data from thesmartphone), as shown in FIG. 5B. Note that this may be different thanthe router connecting to the internet via the smartphone, as in thiscase the router may not necessarily communicate directly with the remotemanagement platform. As a second alternative, Step S111 may includereceiving information from a configuration application on another devicevia push (e.g., over Bluetooth) or via another technique without firstattempting a connection.

Step S112, analyzing internet connection paths, functions to determineaspects of network configuration (e.g., the number and priority ofaccessible internet connections, the existence of a firewall, theexistence of NAT or DHCP servers, etc.) from the router's internetconnection. Step S112 may include analyzing internet connection paths ina number of ways, some of which are described below.

In one example, Step S112 may include analyzing the router's assigned IPaddress to determine network configuration details. If, for example, arouter is assigned a private IP address (e.g., an IPv4 address of192.168.1.104) and has internet connectivity, this may indicate that therouter is connected to the internet by another router. In contrast, ifthe router is assigned a public IP address (e.g., an IPv4 address of8.8.8.8 or an IPv6 address of 2600::aaaa), this may indicate that therouter is directly connected to the internet (e.g., via a cable modem ora DSL modem). In some cases, analysis of the router's IP address canenable an estimation of the geographic location of the router, which canbe leveraged in determining and/or setting the local area networkconfiguration. In some cases, analysis of the router's IP address canenable estimating the bandwidth or other characteristics of the internetconnection (e.g., via a lookup of the ISP providing the IP address).Especially as it relates to those cases in which the local area networkincludes multiple internet connections, a network bandwidth estimate canaid in distributing traffic share suitably across the various internetconnections. In this example, Step S112 may also include analyzing otherdetails related to assigned IP address (e.g., the IP address of the DHCPserver that assigned the router's IP address).

In a second example, Step S112 may include communicating with anexternal server (e.g., through the internet) and analyzing thatcommunication to determine network configuration details. In thisexample, a router could attempt to communicate with an external serveron a number of ports to detect the presence of a firewall. The InternetAssigned Numbers Authority (IANA) maintains a comprehensive database ofthe different ports and their associated data types; for example, port25 is reserved for email traffic within the Simple Mail TransferProtocol (SMTP), while port 80 is designated for world wide web trafficwithin the Hypertext Transfer Protocol (HTTP). Within the context ofthis example, a router could attempt to communicate with an externalserver on a single port, on a predetermined set of ports, on arandomized set of ports, on a set of ports determined from a model, on aset of ports selected for a particular type of traffic, or on a set ofports determined in any other suitable manner. This communication mayinclude a message (or, possibly, multiple messages) which may include asource IP address, a destination IP address, a time stamp, and/or amessage body (and/or possibly additional information). In this example,after attempting to communicate to the external server, the router canwait to receive a response from the external server. The external servermay not receive a message from the router on a particular port; this maybe an indication that traffic has been blocked on that port by afirewall. The external server may receive the message from the router ona particular port and attempt to respond on that same port, but therouter may not receive the response message; this may also be anindication that traffic has been blocked on that port by a firewall. Theexternal server may receive the message from the router and respond witha response message, and the router may receive the response message; inthis case, the router can analyze aspects of the response message (e.g.,time stamp, source IP address, destination IP address, etc.) in order todetermine information about firewall presence and/or configuration. Forexample, if there is a significant time delay between the messageinitiating from the router and being received at the external server(or, alternatively or additionally, a significant time delay between theresponse message initiating from the external server and being receivedat the router), this could be an indication that a firewall hasperformed a filtering process on transmission of both/either therouter's message to the external server and/or the external server'sresponse message to the router. As a second example, if the routerattempts to send multiple messages to the external server on a singleport and receives responses from only a minor fraction of these messages(where, for example, the minor fraction can be set by a predeterminedthreshold), this may also be an indication that a firewall is filteringtraffic on that port. As a third example, if the router attempts to sendmultiple messages to the external server on multiple ports and receivesresponses from the external server on all messages from a first port butonly a fraction of messages sent on a second port, this may be anindication that a firewall is filtering traffic on a particular port. Asa fourth example, firewalls may also perform NAT, and so, for example,by comparing (e.g., at the router, at the external server, etc.) thesource IP address on sending and on receipt and determining that NAT hadbeen performed, one can use this information to help decide if afirewall is present.

In addition to detecting the presence of a firewall, analyzing acommunication between a router and an external server on a number ofports may include identifying particular aspects of a firewall if afirewall is present. For example, one firewall type is a statefulfirewall, in which the firewall explicitly filters traffic depending onstate information of potential traffic (e.g., only passing traffic onpermissible ports, with permissible source or destination IP addresses,and/or abiding by any other suitable criteria). In this example,analyzing responses (or null responses) from attempted communicationsbetween a router and several external servers may enable determinationthat a firewall is both present and only transmitting traffic betweenparticular IP addresses (i.e., the firewall is stateful). A second typeof firewall, a stateless firewall (in which traffic is passed basedsolely on IP addresses contained in a packet header), may also beidentified by analyzing responses (or null responses) between a routerand several external servers.

Additionally or alternatively, the router could send messages (e.g.,Internet Control Message Protocol (ICMP) echo request packets, UserDatagram Protocol (UDP) packets, Transmission Control ProtocolSynchronize (TCP SYN) packets, or any other suitable message or packet)with various configurations to determine further connection information.For example, routers typically decrement packet time-to-live (TTL)values when packets pass through; either by manipulating TTL values forpackets (e.g., performing a traceroute) or by analyzing TTL values, thenumber of hops between the router and an external server (and thus someinformation about network structure) can be determined. Traceroutes inparticular can be performed by the router; the IP addresses ofresponding servers can be used to determine how many hops a packet musttake from the router to the internet (identified by the first public IPaddress responding to the traceroute). Packet response time can also beused to detect the presence of servers or other routers; for instance,network address translation (NAT) may introduce a characteristic delayto packets. In one specific implementation of this example, the routercan perform a traceroute test, which includes sending a sequence ofpackets with a series of integer TTL values to other servers or routers.As the packets hop between network entities, the TTL values aredecremented (e.g., by other routers on the local area network, anexternal server, etc.). When the TTL value of a packet gets decrementedto zero, the network entity can discard the packet and return a messageto the router performing the traceroute. The returned message to therouter can include a packet header, a measurement of the hop round triptime (RTT) of the packets as the packets travel to and from the networkentities, the IP addresses of any of the network entities, and/or anyother suitable information. In one realization of a traceroute test todetect NAT, the traceroute can be used to measure the RTT of packets anddetermine NAT presence based on time delays characteristic of NAT. Inthis example, one can estimate the RTT of packets in the absence of NAT(e.g., by performing traceroute between the router and a network entityfor which it is known a priori that no NAT is being performed, and forwhich the network path between the router and the entity is similar tothe network path between the router and the packet's destination) andcompare the RTT of packets in the absence of NAT to the RTT as measuredby traceroute in the local area network that is to be configured. If thedifference between these two RTTs exceeds a NAT threshold timecharacterized by a time scale for NAT, this can be used to detect thepresence of NAT within the local area network. For example, as shown inFIG. 6A, a packet sent between a router and entity 2 (traveling viaentity 1) experiences a delayd=d ₁ +d ₂ +d ₃ +d ₄ +d ₅ +d ₆ +d ₇where d₁ is the travel time from the router to entity 1, d₂ is theresponse time of entity 1 (i.e., the time taken to successfully forwardthe packet), d₃ is the travel time from entity 1 to entity 2, d₄ is theresponse time of entity 2 (i.e., the time taken to generate a responseto the packet), d₅ is the travel time from entity 2 back to entity 1, d₆is the second response time of entity 1, and d₇ is the travel time fromentity 1 to the router. The example in FIG. 6A assumes that NAT is notperformed at entity 1. If NAT is performed at entity 1, as shown in FIG.6B, the response delays at entity 1 are longer. The response delays maybe characterized as a sum of an initial or base delay (e.g., d2b, d6b)and a delay due to NAT (e.g., d2n, d6n).

A time scale for NAT that can be used for the NAT threshold time can betaken directly from a manufacturer's specification; alternatively, acharacteristic time delay introduced by NAT can be estimated bycomparing the RTT of packets communicated between two servers in whichNAT is performed against the RTT of packets communicated between twoservers in which NAT is not performed. Any other suitable means forcharacterizing a time delay associated with NAT can also be used. TheNAT threshold time can be a number within the range of 0 to 780,000milliseconds but alternatively can span any other suitable range.

In a second realization of a test to detect NAT, packets can be sent(e.g., the initially sent packets, the intermediate packets, the returnpackets, etc.) that include information related to IP addresses in thepacket headers and/or packet bodies which can be analyzed to determineif NAT is being performed on the local area network. In this example, aparticular router can send out packets with an initial source IP addressin the packet header and another network entity can collect a particularpacket with a first received source IP address, as shown in FIG. 7A. Thenetwork entity can then send a response message to the router with thefirst received source IP address in both the packet header and thepacket body, and the router can receive the network entity's responsemessage. The response message that the router receives can contain an IPaddress in the packet header (containing a second received source IPaddress) and an IP address in the packet body (containing the firstreceived source IP address). If NAT is being performed on the local areanetwork, the first received source IP address in the packet header maybe translated to the second received source IP address on hopping to therouter (while the IP address in the packet body may remain fixed), andtherefore a detected difference between the received IP addresses in thepacket header and packet body may indicate that NAT is being performed.Alternatively, if a router sends a packet identifying its IP address inthe body, a receiving server may compare the IP address of the body tothe header source IP of the packet containing it (if they are different,this may be indicative of NAT) and return a response to the router(e.g., directly, or indirectly via the router management platform) asshown in FIG. 7B.

Step S112 may include any suitable communication with an external server(or even an internal server) suitable for aiding in analysis of routerinternet connection paths. In particular, Step S112 may includediscovering network translation characteristics of any NAT serverpresent in the router internet connection path. These characteristicsmay be used to allow the router's NAT server (if operating) to performtranslation in a manner compatible with translation performed by otherNAT servers. For example, in a mesh network in which a NAT server isalready present and in which the router is also intended to be used forNAT, Step S112 may include determining how the pre-existing NAT serverperforms its network translation (i.e., uncovering the pre-existing NATserver's translation table) and configuring the router to functioncompatibly with the pre-existing NAT server.

In a third example, Step S112 may include communicating with a remoterouter management platform. In particular, this is useful for networksincluding multiple smart routers (described in more detail below). Inthis example, Step S112 may include comparing router configuration orregistration data to detected network configuration data. For example,Step S112 may include scanning ports of the router and comparing resultsof the port scan to configured firewall values for the router (if, forexample, more ports are blocked than expected, this may be indicative ofan additional firewall between the router and the remote managementplatform). Communication with a remote router management platform mayinclude any suitable communication (e.g., a heartbeat signal, akeepalive signal, etc.). Routers may transmit heartbeat signals toprovide updates on router status, network status, or any other relevantinformation to the remote management platform. In some cases, the routercan communicate a keepalive signal to the remote management platform.The keepalive signal can be used to ensure that the router and remotemanagement platform maintain their communicative contact, to diagnose abroken link between the router and the remote management platform, tomaintain the connection between multiple NAT-enabled routers on thelocal area network, or for any other suitable purpose. The keepalivesignal can be sent after being prompted by a user, at regular timeintervals (i.e., every week), when changes to the network configurationare detected, or in any other suitable manner.

While the examples described above may be applicable either to networkscontaining a single smart router or to networks containing multiplesmart routers, Step S112 may additionally be performed in mannersspecifically designed to leverage the existence of multiple smartrouters on a network.

For these additional methods to be performed, detection of multiplesmart routers is preferably accomplished by Step S112. The presence ofmultiple smart routers may be detected in any suitable manner.

In one example, multiple smart routers are detected based oncommunication with the remote management platform. In this example, arouter may download configuration data that includes a reference toadditional linked routers (e.g., by MAC address). Here, linked routerspreferably refers to routers that are intended to be on the same LAN(noting that this LAN may be include different subnetworks that arelinked virtually, e.g., through VPN as shown in FIG. 8). Alternatively,this reference to linked routers may be programmed into the router priorto communication with the remote management platform (e.g., if thisinformation was included in a set of routers sold together as a meshnetwork set). Smart routers may additionally or alternatively detectother smart routers in any other suitable manner (e.g., by detecting ahidden access point of another smart router, by detecting a Bluetoothconnection of a smart router, by detecting a particular known SSID,etc.). In some cases, detection of other smart routers is inherentlylinked to a particular network (e.g., when routers are known to be partof a linked mesh network set); in other cases, detection of multiplesmart routers may not mean that the routers should operate on the samenetwork or be administered by the same entity. For example, a smartrouter may detect an open access point of a neighbor's smart router; forthe two to be linked in a mesh network, the link would preferably needto be confirmed by both routers (as opposed to in a linked mesh networkset, where this link may potentially occur automatically). In somecases, the router can be paired with a router identifier and one or moreuser accounts stored in the remote management platform, and informationabout the number of smart routers and their configuration settings(e.g., which, if any, should be DHCP or NAT servers; which, if any,should be linked and isolated on a virtual LAN; details about thetopology of the network; etc.) can be associated with the user accountand stored at the remote management platform. Users can maintain anaccount on servers hosted in the cloud and maintained by the routermanufacturer or other party; this account can be used to performregistration, to perform router configuration, and/or to access routerstatus information. Router registration data can include an ID numberuniquely associated with a particular router (or set of routers) (e.g.,a MAC address, a router group identifier) and can additionally includeinformation regarding the local area network configuration associatedwith the router identifier. In those cases where configuration settingsof the local area network are known a priori by associating the routerwith a router identifier, router configuration data (e.g., DHCP serverconfiguration settings, NAT server configuration settings, wirelessaccess point configuration settings, firewall settings, etc.) can betransmitted from the remote management platform to the router to enablethe router to automatically configure suitable configuration settings ofthe local area network.

Once a set of smart routers are detected and linked together in some wayby the remote management platform (or in another suitable manner), StepS112 may include communicating with each of the linked routers in orderto analyze internet connection paths. In particular, this is useful whenrouters are not in direct connection (e.g., the routers are initiallynot connected by a shared LAN).

For example, a large house can have both a cable modem and a cellularmodem. A first router of a linked set is connected to the cable modem, asecond router of the linked set is connected to the cellular modem, andthe two routers are not otherwise connected. The two routers may bebridged wirelessly so that a user connecting to the wireless network inthe house may use either the cellular internet connection or the cableinternet connection (this is described in more detail in the sectionsdescribing Step S130).

Information for Step S110 may be used not only to identify networkdevice presence and configuration (e.g., presence of a firewall blockinga particular port configuration between a smart router and the internet)but also network device identification. For example, a firewall may beidentified as a particular model of firewall based on a default portblocking ‘fingerprint’ (i.e., how port blocking occurs and for whatports it occurs). As another example, identifying particular clientdevices can be used to perform quality of service (i.e., assigndifferent priority to different devices and to share LAN and/or internetbandwidth across devices based on priority), to assign particulardevices to particular wireless access points or frequencies, or for anyother suitable purpose.

Step S120 includes communicating network data with a remote managementplatform. Step S120 functions to enable data transfer between one orsmart routers and a remote management platform. Step S120 preferablyfunctions to provide router configuration data to routers (e.g., DHCPconfiguration data, firewall configuration data, etc.) and/or aid indetection of network configurations for networks containing smartrouters (as described in Step S110). Step S120 may additionally oralternatively function to keep a remote management platform updated onrouter status (e.g., sending heartbeat signals as previously described).Step S120 may be performed at any time, for any purpose.

Step S130 includes configuring router DHCP and NAT settings. Step S130functions to configure the smart router to serve as a DHCP server (orclient) and/or as a NAT server. Along with NAT configuration, DHCPconfiguration is particularly important for wireless mesh networks; forexample, many mesh network configurations include multiple routers, withonly one router configured as a DHCP/NAT server (the rest mayessentially serve as wireless access points or repeaters).

Step S130 is preferably performed by altering a stored configuration ina remote management platform and then transmitting that storedconfiguration to a smart router, but Step S130 may additionally oralternatively be performed locally on the smart router or in any otherlocation. Step S130 is preferably performed by an electronic devicelinked to the remote management platform (e.g., a smartphone), but mayadditionally or alternatively be performed by any electronic device(e.g., the router itself, the remote management platform by itself,etc.)

Step S130 preferably includes configuring router NAT settings S131, asshown in FIG. 9. Step S131 functions to determine which smart routers ona network (if any) are to serve as NAT servers and to determineconfiguration details for those NAT servers.

In particular, Step S131 is important in cases where there are multiplepotential NAT servers on a network. One common case of this is where auser has existing (non-smart router) networking devices on a network;for example, in situations where a user's cable modem also includes arouter (e.g., a wireless access point with DHCP/NAT/firewall). In thiscase, proper configuration may include disabling NAT in all smartrouters on the network (unless additional private networks are desired).

Another common case occurs when a user has multiple smart routerspresent on a network. In this case, it is important to establish whichsmart routers (preferably all controlled by a remote managementplatform) serve as NAT servers.

Step S131 may include configuring NAT servers in a number of ways,including designating a single NAT server (i.e., one router has NATturned on, the others do not) or by operating multiple NAT servers. IfStep S131 includes configuring any dynamic NAT servers, serverconfigurations are preferably controlled by coordinating smart routersthrough the router management platform; additionally or alternatively,dynamic NAT servers may be managed in any suitable way.

In particular, Step S131 may be used for cases where multiple internetconnections are available. For example, Router 1 may be connected to acable internet connection, while Router 2 may be connected to a cellularinternet connection. Step S131 may be used to perform NAT on Router 1when the cable internet connection is desired, and NAT on Router 2 whenthe cellular internet connection is desired.

In such cases, Step S131 may include operating a single NAT server thatadaptively performs translation (e.g., changing the outside IP to betranslated to/from), operating multiple NAT servers simultaneously(e.g., one for a particular subnet, another for a different subnet),and/or operating multiple NAT servers asynchronously (e.g., operating afirst NAT server by default, but switching to a second NAT server if thefirst NAT server experiences a service interruption).

Step S131 may include configuring NAT servers to share traffic in anysuitable manner. Traffic sharing preferably includes sharing trafficacross multiple internet connections (which correspond to differentpublic IPs used by NAT). For example, Step S131 may include designatingprimary and secondary (and tertiary, and so on) internet connections,used by all devices on a particular network. Step S131 may additionallyor alternatively include designating internet connection by device(e.g., all devices in the 192.168.1.xxx subnet use a particularconnection, all smartphones use a particular connection, etc.). StepS131 may additionally or alternatively include designating internetconnection by TCP stream (or at any other sub-device resolution level);for example, high bandwidth, latency insensitive applications (e.g.,streaming video) may use a first connection, while low bandwidth,latency sensitive applications (e.g., real-time online gaming) may use asecond connection.

Step S131 may include sharing traffic based on any suitable input data.For example, Step S131 may include altering NAT configuration based onavailable bandwidth (e.g., a particular connection is only used until abandwidth cap is reached), price (e.g., expensive connections may beused only when necessary for a particular application), or any othercriteria. Traffic sharing agreements are preferably determined by therouter management platform, but may additionally or alternatively bedetermined by any suitable entity.

Traffic sharing can also be accomplished via network load balancingalgorithms, whereby IP traffic is distributed over the multiple internetconnections in order to meet one or more network goals. Examples ofnetwork goals may include reducing response time for one or more deviceson the network, increasing bandwidth available to one or more devices onthe network, increasing performance for particular services or types oftraffic on the network, increasing reliability of internet access fordevices on the network, etc. A first example of a network load balancingalgorithm for traffic sharing is a round robin algorithm. The roundrobin algorithm allocates a first IP traffic request to a randomlyselected first internet connection, a second traffic request to a secondinternet connection that is randomly selected except that it excludesthe first, and so on until all internet connections have been allocatedat least once, at which point the cycle repeats. Round robin works wellwhen most traffic requests are roughly equal in bandwidth demand andduration. A second example of a network load balancing algorithm isdynamic round robin. Dynamic round robin works similarly to the baseround robin algorithm except that the allocation step is distributedaccording to a weighting scheme discerned from real-time internetconnection performance. Dynamic round robin can eschew the problem ofmultiple high traffic requests being routed over the same internetconnection. A third example of a network load balancing algorithm is apredictive algorithm. A predictive algorithm can monitor real-timeinternet connection characteristics (e.g., which internet connectionshave the fewest IP traffic requests on them, which internet connectionshave the largest data stream allocations on them, etc.) and historicalinternet connection characteristics (e.g., a time series of monitoreddownload and upload speeds over a recent time period) in order todetermine which internet connections are improving or declining inperformance over time (as quantified in a metric of performance), canfeed these metrics of performance into a dynamic weighting scheme, andcan allocate new IP traffic requests according to the dynamic weightingscheme. Alternatively, any suitable network load balancing algorithm canbe implemented.

Instead of or in addition to sharing traffic over multiple internetconnections, traffic can also be shared over multiple smart routers.Load balancing, traffic sharing agreements, or any other suitable meansfor determining how traffic is shared across the different routers canbe implemented to accomplish similar network goals as for trafficsharing over multiple internet connections (e.g., increased networkbandwidth, speed, reliability, performance, etc.).

The manner in which the network performs load balancing can bepredetermined (e.g., traffic can be proportionally distributed acrossinternet connections), dynamically determined (e.g., at the time of auser request, the particular request can assign a priority, and then therouters can handle load performance in accordance with the priorityhierarchy of all network traffic), or determined in any other suitablemanner.

Step S130 preferably includes configuring router DHCP settings S132, asshown in FIG. 9. Step S132 functions to determine which smart routers ona network (if any) are to serve as DHCP servers and to determineconfiguration details for those DHCP servers.

In particular, Step S132 is important in cases where there are multiplepotential DHCP servers on a network. One common case of this is where auser has existing (non-smart router) networking devices on a network;for example, in situations where a user's cable modem also includes arouter (e.g., a wireless access point with DHCP/NAT/firewall). In thiscase, proper configuration may include disabling DHCP in all smartrouters on the network (unless additional private networks are desired).

Another common case occurs when a user has multiple smart routerspresent on a network. In this case, it is important to establish whichsmart routers (preferably all controlled by a remote managementplatform) serve as DHCP servers.

Step S132 may include configuring DHCP servers in a number of ways,including designating a single DHCP server (i.e., one router has DHCPturned on, the others do not) or by operating multiple DHCP servers. IfStep S132 includes configuring any dynamic DHCP servers, serverconfigurations are preferably controlled by coordinating smart routersthrough the router management platform; additionally or alternatively,dynamic DHCP servers may be managed in any suitable way.

If Step S132 includes operating multiple DHCP servers, the DHCP serverspreferably share an IP table (e.g., DHCP servers assign IP addresses todevices and the assignments are stored in a table accessible to themultiple servers so that they do not attempt to assign different IPaddresses to the same device).

Additionally or alternatively, Step S132 may include configuring DHCPservers to share IP assignment in any suitable manner. For example, StepS132 may include designating primary and secondary (and tertiary, and soon) DHCP servers, used by all devices on a particular network. Step S132may additionally or alternatively include designating DHCP server bydevice (e.g., all devices with one MAC address range use a particularDHCP server) or by desired subnet (preferably configured by the remotemanagement platform). Step S132 may include sharing IP assignment dutiesbased on any suitable input data.

Step S140 includes configuring router firewall settings. Step S140functions to determine which smart routers on a network (if any) are toserve as firewalls and to determine configuration details for thosefirewalls.

In particular, Step S140 is important in cases where there are multiplepotential firewalls (software OR hardware) on a network. One common caseof this is where a user has existing (non-smart router) networkingdevices on a network; for example, in situations where a user's cablemodem also includes a router (e.g., a wireless access point withDHCP/NAT/firewall). In this case, proper configuration may includedisabling firewalls in all smart routers on the network (unlessadditional protection is desired).

Another common case occurs when a user has multiple smart routerspresent on a network. In this case, it is important to establish whichsmart routers (preferably all controlled by a remote managementplatform) serve as firewalls.

In general, Step S140 preferably includes operating firewalls on anyrouter performing NAT but may additionally or alternatively includeoperating firewalls (or not) on any smart router.

Step S140 preferably includes configuring firewalls based onconfiguration data stored in the remote management platform but mayadditionally or alternatively configure firewalls in any suitablemanner.

Step S150 includes prompting user intervention. Step S150 functions toenable users to reconfigure devices on the network not controlled by theremote management platform (e.g., non-smart-router networking devices orsmart routers inaccessible to the remote management platform). Forexample, Step S150 may include providing a user instructions toreconfigure a modem with an integrated router to disable NAT, DHCP, andfirewall, allowing a smart router to take over these functions.

Step S150 preferably includes instructing a user to perform networkconfiguration in any suitable way (including providing instructions forchanging network device configurations in software, rerouting Ethernetcables, moving wireless access points, etc.), as shown in FIG. 10A. Inone example, the user wants to modify network configuration settings(including DHCP servers, NAT servers, wireless access points, firewalls,etc.) after the previous steps have been performed. Step S150 enablesthe user (most preferably by means of software operating in conjunctionwith a remote management platform, but alternatively otherwise) toeasily implement the desired configuration changes. In a second example,the user can confirm that the network configuration performed by theearlier steps are appropriate. In this second example, the user is giveninstructions through software on an external electronic device; per theinstructions, the user can then reconfigure network configurationsettings when the reconfiguration includes physical modifications tonetwork features (e.g., disconnecting routers which were previouslyphysically tethered by an Ethernet cable).

In a variation of a preferred embodiment, Step S150 performs some or allof reconfiguration of other devices desired. For example, software on asmart router (or in the remote management platform, if the web interfaceis accessible to the platform) may automatically perform thereconfiguration desired, as shown in FIG. 10B. For example, Step S150may include requesting a user identifier (e.g., credential, accountname, password, access code, etc.) and network entity identifiers (e.g.,identifying the other devices as routers, servers, etc.; identifying themanufacturers or model numbers of the other devices; etc.) in theprocess of reconfiguration. In this example, Step S150 may include theuser providing the network entity identifiers (e.g., via a userinterface on a user electronic device, through a web interfaceaccessible to the remote management platform, etc.) and/or the networkentity identifiers being detecting automatically.

As one of ordinary skill in the art will recognize, suitablecombinations of the method steps can be readily envisioned and performedin a diverse range of contexts. In a first example, a method for routerconfiguration can include collecting DHCP server presence data of alocal area network at a router; collecting NAT server presence data ofthe local area network at the router; generating a network configurationstatus based upon the DHCP server presence data and the NAT serverpresence data; and configuring DHCP server and NAT server settings ofthe router based on the network configuration status. This example canadditionally include detecting and configuring firewall settings of thelocal area network; detecting and configuring wireless access points ofthe local area network; designating a hierarchy of internet connections(e.g., primary and secondary internet connections) during theconfiguration of the NAT server settings; and/or storing the networkconfiguration status at a remote management platform. In this example,the router can detect the local area network configuration and topology,which may already include, for example, other routers, NAT servers, orDHCP servers, each of which may be connected to each other in a varietyof ways). Further, in this example, the router can identify the otherentities (e.g., DHCP servers, NAT servers, firewalls, wireless accesspoints, smart routers, non-smart routers, etc.) on the local areanetwork and suitably configure itself based on presence and/orconfiguration of the entities on the local area network, allautomatically and without requiring prior knowledge of the constituentelements contained in the local area network. This example can beespecially useful for mesh network configuration, where the routermanagement platform can facilitate the automatic detection of thevarious entities in the local area network and configure one or moreentities to work in tandem (e.g., one router as a gateway and otherrouters serving as wireless repeaters or wireless access points). Thisexample can also enable anyone authorized to access the remotemanagement platform to aid in configuring the router (e.g., when theuser is having trouble configuring the local area network) via asecondary internet connection (e.g., tethered cellular internetconnection), even when the router's primary internet connection (e.g., acable modem) is down.

In a second example, a method for router configuration includesestablishing an internet connection at a router; transmitting a routeridentifier of the router to a remote management platform via theinternet connection; at the remote management platform, identifying alocal area network configuration (including DHCP server configurationsettings, NAT server configuration settings, firewall settings, andwireless access point configuration settings) associated with the routeridentifier; transmitting the local area network configuration from theremote management platform to the router; and at the router, configuringthe DHCP server configuration settings, NAT server configurationsettings, firewall settings, and wireless access point configurationsettings based on the local area network configuration. This example canadditionally include connecting to a user mobile electronic device andreceiving the local area network configuration from the user mobileelectronic device; connecting to a cellular internet connection of theuser mobile electronic device to request the local area networkconfiguration from the remote management platform; and/or updating thelocal area network configuration with a user device. In this example,the router can identify a local area network configuration by retrievingthe configuration data from the remote management platform over theinternet and can automatically configure the local area network entities(e.g., DHCP servers, NAT servers, firewalls, wireless access points,smart routers, non-smart routers, etc.) based upon the configurationdata retrieved from the remote management platform. In this example, therouter can specifically leverage additional, a priori knowledge of thelocal area network configuration and topology in order to configure alllocal area network entities to work in tandem. This example realizesmany of the benefits of the first example but can eschew explicitlydetecting the local area network configuration, which may expedite theprocess for automatic configuration.

The methods of the preferred embodiment and variations thereof can beembodied and/or implemented at least in part as a machine configured toreceive a computer-readable medium storing computer-readableinstructions. The instructions are preferably executed bycomputer-executable components preferably integrated with a smartrouter. The computer-readable medium can be stored on any suitablecomputer-readable media such as RAMs, ROMs, flash memory, EEPROMs,optical devices (CD or DVD), hard drives, floppy drives, or any suitabledevice. The computer-executable component is preferably a general orapplication specific processor, but any suitable dedicated hardware orhardware/firmware combination device can alternatively or additionallyexecute the instructions.

As a person skilled in the art will recognize from the previous detaileddescription and from the figures and claims, modifications and changescan be made to the preferred embodiments of the invention withoutdeparting from the scope of this invention defined in the followingclaims.

What is claimed is:
 1. A wireless mesh apparatus, comprising: aprocessor; one or more wireless local area network (WLAN) interfacesoperably coupled to the processor; a wired network interface operablycoupled to the processor; and a memory operably coupled to theprocessor, the memory storing computer-readable instructions operative,when executed, to cause the processor to: receive, from one or morewireless mesh devices of a local area network, network configurationdata including dynamic host configuration protocol (DHCP) serverpresence data of the local area network; receive, from the one or morewireless mesh devices, mesh router presence data, the mesh routerpresence data indicating a presence of the one or more wireless meshdevices; generate network configuration information based upon the DHCPserver presence data and the mesh router presence data; determine, overthe wired network interface, a wide area network (WAN) connection;establish a wireless connection to a hidden restricted wireless localarea network implemented by one of the one or more wireless meshdevices; send the network configuration information and a deviceidentifier corresponding to the wireless mesh apparatus to a remotenetwork management server over the wireless connection, wherein thedevice identifier is associated with a user account that is associatedwith the one or more wireless mesh devices; receive mesh configurationinformation associated with the user account from a remote networkmanagement server over the wireless connection; and configure one ormore configuration settings based on the mesh configuration information,wherein at least a portion of the mesh configuration information isoperable to cause the wireless mesh apparatus to operate in a wirelessmesh network including at least one of the one or more wireless meshdevices, wherein the one of the one or more wireless mesh devices isoperative to implement the hidden restricted wireless local area networkwithout broadcasting a service set identifier corresponding to thehidden restricted wireless local area network.
 2. The wireless meshapparatus of claim 1, wherein the network configuration data furthercomprises network address translation (NAT) server presence data of thelocal area network, the NAT server presence data indicating a presenceof a NAT server on the local area network.
 3. The wireless meshapparatus of claim 1, wherein the computer-readable instructions arefurther operative to cause the processor to: determine one or morechanges in the network configuration data and mesh device presence data,and generate, and transmit, the network configuration information inresponse to the one or more changes.
 4. The wireless mesh apparatus ofclaim 1, wherein the mesh configuration information is operative tocause the wireless mesh apparatus to operate as a Network AddressTranslation (NAT) server.
 5. The wireless mesh apparatus of claim 1,wherein the mesh configuration information is operative to cause thewireless mesh apparatus to operate as a Dynamic Host ConfigurationProtocol (DHCP) server.
 6. The wireless mesh apparatus of claim 1,wherein the mesh configuration information is operative to cause thewireless mesh apparatus to operate as a gateway.
 7. The wireless meshapparatus of claim 1, wherein the mesh configuration information isoperative to cause the wireless mesh apparatus to operate as an accesspoint.
 8. A wireless networking system, comprising: a plurality ofwireless mesh devices, comprising a first wireless mesh device operativeto: receive, from one or more other wireless mesh devices of theplurality of wireless mesh devices of a local area network, networkconfiguration data including dynamic host configuration protocol (DHCP)server presence data of the local area network; receive, from the one ormore other wireless mesh devices, mesh device presence data, the meshdevice presence data indicating a presence of the one or more otherwireless mesh devices; generate network configuration information basedupon the DHCP server presence data and the mesh device presence data;determine, over a wired network interface of the first wireless meshdevice, a wide area network (WAN) connection; establish a wirelessconnection to a hidden restricted wireless local area networkimplemented by one of the one or more other wireless mesh devices; andsend the network configuration information and a device identifieruniquely corresponding to the first wireless mesh device and the networkconfiguration information to a remote network management server over thewireless connection; and the remote network management server operativeto: receive the device identifier and the network configurationinformation from the first wireless mesh device; link the first wirelessmesh device to a set of wireless mesh devices comprising one or more ofthe one or more other wireless mesh devices in association with a useraccount by storing device identifiers associated with the set ofwireless mesh devices; and transmit mesh configuration informationassociated with the user account to the first wireless mesh device,wherein at least a portion of the mesh configuration information isoperative to cause the first wireless mesh device to jointly implement asingle wireless mesh network including the set of wireless mesh devices;and wherein the one of the one or more other wireless mesh devices isoperative to implement the hidden restricted wireless local area networkwithout broadcasting a service set identifier corresponding to thehidden restricted wireless local area network.
 9. The wirelessnetworking system of claim 8, wherein the first wireless mesh device isfurther operative to determine one or more changes in the networkconfiguration data and the mesh device presence data, and generate, andtransmit, the network configuration information in response to the oneor more changes.
 10. The wireless networking system of claim 8, whereinthe one of the one or more other wireless mesh devices is furtheroperative to only allow connections on the hidden restricted wirelesslocal area network to devices corresponding to a same routermanufacturer as the one of the one or more other wireless mesh devices.11. The wireless networking system of claim 8, wherein the one of theone or more other wireless mesh devices is further operative to onlyallow connections on the hidden restricted wireless local area networkto devices having one or more credentials or characteristics.
 12. Thewireless networking system of claim 8, wherein: the one or more otherwireless mesh devices each comprise a Bluetooth interface; and whereineach of the one or more other wireless mesh devices is further operativeto establish, over the Bluetooth interface, a connection to a first userelectronic device executing a configuration application and receiveconfiguration information from the first user electronic device.
 13. Thewireless networking system of claim 8, wherein the remote networkmanagement server is operative to compare wireless mesh registrationdata to the network configuration data received from the one or moreother wireless mesh devices.
 14. The wireless networking system of claim8, wherein the remote network management server is operative to: comparewireless mesh registration data to the network configuration datareceived from the one or more other wireless mesh devices; and transmitconfiguration data that includes references to one or more wireless meshdevices not identified in the network configuration data.
 15. Thewireless networking system of claim 8, wherein the remote networkmanagement server is further operative to interact with a plurality oflinked wireless mesh devices to analyze network connection paths amongthe first wireless mesh device and the set of wireless mesh devices. 16.The wireless networking system of claim 8, wherein the meshconfiguration information is operative to cause a selected one of theone or more other wireless mesh devices to operate as a Network AddressTranslation (NAT) server.
 17. The wireless networking system of claim 8,wherein the mesh configuration information is operative to cause aselected one of the one or more other wireless mesh devices to operateas a Dynamic Host Configuration Protocol (DHCP) server.
 18. The wirelessnetworking system of claim 8, wherein the mesh configuration informationis operative to cause a selected one of the one or more other wirelessmesh devices to operate as a gateway and others of the one or more otherwireless mesh devices to operate as access points.
 19. A wireless meshapparatus, comprising a processor; one or more wireless local areanetwork (WLAN) interfaces operably coupled to the processor; a wirednetwork interface operably coupled to the processor; a memory operablycoupled to the processor, the memory storing computer-readableinstructions operative, when executed, to cause the processor to:receive, from one or more wireless mesh devices of a local area network,network configuration data including dynamic host configuration protocol(DHCP) server presence data of a local area network; receive, from oneor more wireless mesh devices of the local area network, mesh routerpresence data, the mesh router presence data indicating a presence ofthe one or more wireless mesh devices; generate network informationbased upon the DHCP server presence data and the mesh router presencedata; determine, over the wired network interface, a wide area network(WAN) connection; establish, over the WAN connection, a wirelessconnection to a hidden restricted WLAN implemented by one of the one ormore wireless mesh devices; send the network information and a deviceidentifier corresponding to the wireless mesh apparatus to a remotenetwork management server over the WAN connection to the hiddenrestricted WLAN, wherein the device identifier is associated with a useraccount that is associated with the one or more wireless mesh devices;receive, from the remote network management server, mesh configurationinformation responsive to the remote network management server receivingthe network information and the device identifier; and configure one ormore configuration settings based on the mesh configuration information,wherein at least a portion of the mesh configuration information isoperable to cause the wireless mesh apparatus to operate in a wirelessmesh network including at least one of the one or more wireless meshdevices, and wherein the one of the one or more wireless mesh devices isoperative to implement the hidden restricted WLAN without broadcasting aservice set identifier corresponding to the hidden restricted WLAN. 20.The wireless mesh apparatus of claim 19, wherein the wireless meshapparatus is further operative to receive an indication of one or morechanges in the mesh router presence data, and generate, and transmit,the network information in response to the one or more changes in themesh router presence data.